What's New

The content of this document describes version 16.4 Update 6, released 2020-03-06.

16.4

[16.4] New Identity Provider-based authentication replaces NTLM-based authentication for Windows Active Directory (see User authentication and Identity Providers, Identity Provider (IdP) setup).

[16.4] Requirements changes for SQL Server and databases (see Hardware and software requirements).

[16.4] Role names and categories have had major revisions (see Tenant roles).

[16.4] New ZIP-based installation for the IPS PowerShell module (see IPS PowerShell module (Automation cmdlets)).

[16.4] IPS Server Monitor now shows CPU, Memory and Thread usage for individual application processes (see IPS Server monitoring).

Important for PlanningSpace deployments upgraded from version 16.3 to 16.4: For optimal performance it is recommended for every database to set the option 'Legacy Cardinality Estimation' to 'ON'.

 

[16.4 U1] Azure Active Directory and Citrix NetScaler are now supported as Identity Providers for user authentication (see User authentication and Identity Providers.)

[16.4 U1] Added functions in the IPS Manager UI to import SAML identity provider metadata, and export SAML service provider metadata (see PlanningSpace tenant IdP configuration).

 

[16.4 U2] This Update features significant performance improvements for Dataflow and Reserves (see the Release Notes for details).

[16.4 U2] New version of the PlanningSpace Data Connector add-in (fixes an issue where data in a vertical range of Excel cells would not update correctly).

 

[16.4 U5] New Dataflow application server setting 'RunReportsIndependently' (see Applications settings).

[16.4 U5] Reconciliations are now 'soft' deleted in the PlanningSpace application, i.e. the data are not deleted from the tenant database. IPS Administrators should configure a cleanup scheduler to remove redundant data at times when users will not be inconvenienced (database tables are locked during deletions and users may not be able to run the Reconciliation application). This is done using the 'Reconciliation Cleanup' application settings, see Reconciliation cleanup. Note that the cleanup scheduled task is disabled by default. The cleanup task may require additional database storage to operate.